It might look like there are duplicates, but that's just cause there are 2 encounter slots for each area. So we need them to be possible on each slot.

Say for diamond, for example. Each of the "special" pokemon, when selected, have a 10% encounter rate in that area. It's the same for every pokemon. But that 10% is distributed across 2 different encounter slots. This is because it decreases the encounter rate for 2 separate pokemon by 5% each (by replacing that slot). So there are a lot of what seem like duplicates, but they are just in different encounter slots.

The same is true for platinum, there are 2 5% "wooper" encounters that are replaced by the 2 5% encounters for the selected pokemon.

For D/P, its either encounter_slot_id 7 or 8

For Plat, its either encounter_slot_id 129 or 130.

It might look like there are duplicates, but that's just cause there are 2 encounter slots for each area. So we need them to be possible on each slot.

Say for diamond, for example. Each of the "special" pokemon, when selected, have a 10% encounter rate in that area. It's the same for every pokemon. But that 10% is distributed across 2 different encounter slots. This is because it decreases the encounter rate for 2 separate pokemon by 5% each (by replacing that slot). So there are a lot of what seem like duplicates, but they are just in different encounter slots.

The same is true for platinum, there are 2 5% "wooper" encounters that are replaced by the 2 5% encounters for the selected pokemon.

For D/P, its either encounter_slot_id 7 or 8

For Plat, its either encounter_slot_id 129 or 130.

Ok, thanks for the explanation. I've done a more thorough review and the encounters are looking good - thank you for adding these in! All that's left is to address the previous comments I left. I'll take a look at your other PRs soon as well.

Oh no! :((( Merge conflicts :)

sorry guys!

Ok, fixed conflicts, shifted all the ids down.

A PokeAPI/api-data refresh has started. In ~45 minutes the staging branch of PokeAPI/api-data will be pushed with the new generated data.

The staging branch will be deployed in our staging environment and the entire API will be ready to review.

A Pull Request (master<-staging) will be also created at PokeAPI/api-data and assigned to the PokeAPI Core team to be reviewed. If approved and merged new data will soon be available worldwide at pokeapi.co.

The updater script has finished its job and has now opened a Pull Request towards PokeAPI/api-data with the updated data.

The Pull Request can be seen deployed in our staging environment when CircleCI deploy will be finished (check the start time of the last build).